Skip to content

Conversation

@ErlendLandro
Copy link
Contributor

No description provided.

@ErlendLandro ErlendLandro requested a review from mairaw as a code owner April 11, 2018 14:15
Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @Mackiovello for your contribution. I left a note on how we usually style GitHub repo links. Please take a look!

## Build the CLR from source

The source code for the .NET CoreCLR can be found in [the `dotnet/coreclr` repository on GitHub](https://github.com/dotnet/coreclr/).
The source code for the .NET CoreCLR can be found in [the CoreCLR repository on GitHub](https://github.com/dotnet/coreclr/).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When we refer to repo names, we usually refer to them as the GitHub path. The sentence as it was tells users what it is: the .NET CoreCLR and where it is: dotnet/coreclr.

So for consistency, I'd keep it like that.

However, I think we can improve the readability of that sentence by making a change like this:
can be found in the [dotnet\coreclr](https://github.com/dotnet/coreclr/) repository on GitHub.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense. I wanted to make it consistent with the link further down the page that looks like this:
at the base of [the CoreCLR repository](https://github.com/dotnet/coreclr/)

I'll make both of them the same format then: the [org-name/repo-name] repository

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch @Mackiovello! Yes, that would be perfect!

The links had different formats. This makes them consistently follow the format of `[org-name/repo-name](link-to-repo)`
Copy link
Contributor

@mairaw mairaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look great! Thank you so much @Mackiovello. Your fix should go live within a day or so.

@mairaw mairaw merged commit a4f8537 into dotnet:master Apr 11, 2018
@ErlendLandro ErlendLandro deleted the patch-2 branch April 11, 2018 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants